Viewing CESID Logs

To view Customer Emergency Services ID (CESID) logs:

 

NOTES

 

Log File Storage

The logs, starting with the oldest, are overwritten when the maximum file size of 5000 records is reached.

How to use the CESID logs

The following table describes scenarios that may generate CESID Logs and/or alarms and what kind of corrective action the system administrator can take.

NOTE: In the table below, a "known" L2 port is a port that is mapped to a CESID in the L2 to CESID Mapping table. An "unknown" L2 port is a port for which there is no L2 to CESID Mapping.

Scenario

Resulting System Behavior

Corrective Action

A newly registered IP device has not been assigned a CESID in the CESID Assignment form and is connecting through an unknown L2 port.

  • An entry will be created in the L2 to CESID Mapping table, using the L2 data from the primary protocol; however, the CESID value will be missing.

  • A CESID Alarm is generated.

  • A log is generated: "Device Registration. No CESID Available."

Assign missing CESID.

A newly registered IP device has been assigned a CESID in the CESID Assignment form and is connecting through an unknown L2 port.

  • No alarm is generated.

  • A new entry is created in the L2 to CESID Mapping table, using the L2 data from the primary protocol and the CESID from the CESID Assignment form.

None required.

A previously known or newly registered device has been assigned a CESID in the CESID Assignment form and is connecting through a known L2 port.

  • No alarm is generated.

  • No log is generated.

None required.

A moved device registers at an unknown L2 port.

  • A CESID alarm is generated.

  • Also, if a CESID for the registering DN exists in the CESID Assignment form, the CESID will be cleared and the following log is generated: "Device Move. No CESID Available at new L2 port. CESID Assignment cleared."

Assign missing CESID.

A new or known device registers to a known L2 port, but the CESID for that L2 port does not match the one defined in the CESID Assignment form.

  • A CESID alarm is generated.

  • The system clears the CESID and CESID Comments in the CESID Assignment form and also clears the CESID in the L2 to CESID Mapping table. The following log is generated: "Device Move. No CESID Available at new L2 port. CESID Assignment cleared."

Assign missing CESID.

A device moves to a known L2 port.

  • No alarm is generated.

  • The system updates the CESID Assignment table with the CESID from the L2 to CESID Mapping table. The following log is generated: "Device Move. CESID=<X>. Source=L2 to CESID Mapping."

None required.

A new device registers to a known L2 port but does not have a CESID in the CESID Assignment form.

  • No alarm is generated.

  • The device CESID is updated in the CESID Assignment form, using the CESID from the L2 to CESID Mapping table. The following log is generated: "Device registration. CESID=<X>. Source=L2 to CESID Mapping."

None required.